<!DOCTYPE html> 
<html> 
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1"> 
	<title>jQuery Mobile Docs - Events</title> 
	<link rel="stylesheet"  href="../../themes/default/" /> 
	<link rel="stylesheet" href="../_assets/css/jqm-docs.css"/>
	<script src="../../js/jquery.js"></script>
	<script src="../../experiments/themeswitcher/jquery.mobile.themeswitcher.js"></script>
	<script src="../_assets/js/jqm-docs.js"></script>
	<script src="../../js/"></script>
</head> 
<body> 

<div data-role="page" class="type-interior">

	<div data-role="header" data-theme="f">
		<h1>Events</h1>
		<a href="../../index.html" data-icon="home" data-iconpos="notext" data-direction="reverse" class="ui-btn-right jqm-home">Home</a>
	</div><!-- /header -->

	<div data-role="content">
		<div class="content-primary">

		<p>jQuery Mobile offers several custom events that build upon native events to create useful hooks for development. Note that these events employ various touch, mouse, and window events, depending on event existence, so you can bind to them for use in both handheld and desktop environments. You can bind to these events like you would with other jQuery events, using <code>live()</code> or <code>bind()</code>.</p>
		
			<div class="ui-body ui-body-e">
		<h4 style="margin:.5em 0">Important: Use pageCreate(), not $(document).ready()</h4>
		The first thing you learn in jQuery is to call code inside the $(document).ready() function so everything will execute as soon as the DOM is loaded. However, in jQuery Mobile, Ajax is used to load the contents of each page into the DOM as you navigate, and the DOM ready handler only executes for the first page. To execute code whenever a new page is loaded and created, you can bind to the <code><strong>pagecreate</strong></code> event. This event is explained in detail at the bottom of this page.</div>
		
		<h2>Touch events</h2>
		<dl>
			<dt><code>tap</code></dt>
			<dd>Triggers after a quick, complete touch event.</dd>
			
			<dt><code>taphold</code></dt>
			<dd>Triggers after a held complete touch event (close to one second).</dd>
			
			<dt><code>swipe</code></dt>
			<dd><p>Triggers when a horizontal drag of 30px or more (and less than 20px vertically) occurs within 1 second duration but these can be configured:</p>
			  <ul>
			  	<li><code>scrollSupressionThreshold</code> (default: 10px) – More than this horizontal displacement, and we will suppress scrolling</li>
			  	<li><code>durationThreshold</code> (default: 1000ms) – More time than this, and it isn’t a swipe</li>
			  	<li><code>horizontalDistanceThreshold</code> (default: 30px) – Swipe horizontal displacement must be more than this.</li>
			  	<li><code>verticalDistanceThreshold</code> (default: 75px) – Swipe vertical displacement must be less than this.</li>
			  	</ul>
			</dd>
			
			<dt><code>swipeleft</code></dt>
			<dd>Triggers when a swipe event occurred moving in the left direction.</dd>
			
			<dt><code>swiperight</code></dt>
			<dd>Triggers when a swipe event occurred moving in the right direction.</dd>
			</dl>
		<h2>Orientation change event</h2>
		<dl>
			<dt><code>orientationchange</code></dt>
			<dd>Triggers when a device orientation changes (by turning it vertically or horizontally). When bound to this event, your callback function can leverage a second argument, which contains an <code>orientation</code> property equal to either "portrait" or "landscape". These values are also added as classes to the HTML element, allowing you to leverage them in your CSS selectors. Note that we currently bind to the resize event when orientationChange is not natively supported.</dd>
		</dl>
			
		<h2>Scroll events</h2>
		<dl>
			<dt><code>scrollstart</code></dt>
			<dd>Triggers when a scroll begins. Note that iOS devices freeze DOM manipulation during scroll, queuing them to apply when the scroll finishes. We're currently investigating ways to allow DOM manipulations to apply before a scroll starts.</dd>
		</dl>
		<dl>
			<dt><code>scrollstop</code></dt>
			<dd>Triggers when a scroll finishes.</dd>
		</dl>	
		
		<h2>Page show/hide events</h2>
		<p>Whenever a page is shown or hidden in jQuery Mobile, two events are triggered on that page. The events triggered depend on whether that page is being shown or hidden, so when a page transition occurs, there are actually 4 events triggered: 2 for each page. </p>
		<dl>
			<dt><code>pagebeforeshow</code></dt>
			<dd>Triggered on the page being shown, before its transition begins.</dd>
			
			<dt><code>pagebeforehide</code></dt>
			<dd>Triggered on the page being hidden, before its transition begins.</dd>
			
			<dt><code>pageshow</code></dt>
			<dd>Triggered on the page being shown, after its transition completes.</dd>
			
			<dt><code>pagehide</code></dt>
			<dd>Triggered on the page being hidden, after its transition completes.</dd>
			
		</dl>
		
		<p>Note that all four of these events expose a reference to either the next page (<code>nextPage</code>) or previous page (<code>prevPage</code>), depending on whether the page is being shown or hidden, and whether that next or previous page exists (the first ever page shown does not have a previous page to reference, but an empty jQuery object is provided just the same). You can access this reference via the second argument of a bound callback function. For example: </p>
<pre><code>
$('div').live('pageshow',function(event, ui){
  alert('This page was just hidden: '+ ui.prevPage);
});

$('div').live('pagehide',function(event, ui){
  alert('This page was just shown: '+ ui.nextPage);
});
</code></pre>
		<p>Also, for these handlers to be invoked during the initial page load, you must bind them before jQuery Mobile executes.  This can be done in the <code>mobileinit</code> handler, as described on the <a href="globalconfig.html">global config</a> page.
		<h2>Page initialization events</h2>
		
		<p>Internally, jQuery Mobile auto-initializes plugins based on the markup conventions found in a given "page". For example, an <code>input</code> element with a <code>type</code> of <code>range</code> will automatically generate a custom slider control.</p>
		
		<p>This auto-initialization is controlled by the "page" plugin, which dispatches events before and after it executes, allowing you to manipulate a page either pre-or-post initialization, or even provide your own intialization behavior and prevent the auto-initializations from occuring. Note that these events will only fire once per "page", as opposed to the show/hide events, which fire every time a page is shown and hidden.</p>	
			
		<dl>
			<dt><code>pagebeforecreate</code></dt>
			<dd>
				<p>Triggered on the page being initialized, before initialization occurs.</p>
<pre><code>
$('#aboutPage').live('pagebeforecreate',function(event){
  alert('This page was just inserted into the dom!');
});
</code></pre>
				<p>Note that by binding to <code>pagebeforecreate</code> and returning <code>false</code>, you can prevent the page plugin from making its manipulations.</p>
		
<pre><code>
$('#aboutPage').live('pagebeforecreate',function(event){
  //run your own enhancement scripting here...
  return false;
});
</code></pre>		
			</dd>
			
			<dt><code>pagecreate</code></dt>
			<dd>
				<p>Triggered on the page being initialized, after initialization occurs. We recommend binding to this event instead of DOM ready() because this will work regardless of whether the page is loaded directly or if the content is pulled into another page as part of the Ajax navigation system.</p>
<pre><code>
$('#aboutPage').live('pagecreate',function(event){
  alert('This page was just enhanced by jQuery Mobile!');
});
</code></pre>
			</dd>
		</dl>

		
		
		<h2>Virtual mouse events</h2>
		<p>We provide a set of "virtual" click events that normalize mouse and touch events. This allows the developer to register listeners for the basic mouse events, such as mousedown, mousemove, mouseup, and click, and the plugin will take care of registering the correct listeners behind the scenes to invoke the listener at the fastest possible time for that device. This still retains the order of event firing in the traditional mouse environment, should multiple handlers be registered on the same element for different events.</p>
		<dl>
			<dt><code>vmouseover</code></dt>
			<dd>Normalized event for handling touch or mouse <code>mouseover</code> events</dd>
			
			<dt><code>vmousedown</code></dt>
			<dd>Normalized event for handling touch or mouse <code>mousedown</code> events</dd>
			
			<dt><code>vmousemove</code></dt>
			<dd>Normalized event for handling touch or mouse <code>mousemove</code> events</dd>
			
			<dt><code>vmouseup</code></dt>
			<dd>Normalized event for handling touch or mouse <code>mouseup</code> events</dd>
			
			<dt><code>vclick</code></dt>
			<dd>Normalized event for handling touch or mouse <code>click</code> events</dd>
			
			<dt><code>vmousecancel</code></dt>
			<dd>Normalized event for handling touch or mouse <code>mousecancel</code> events</dd>
		</dl>
		
		
		
		<h2>Animation Events</h2>
		<p>jQuery Mobile exposes the <code>animationComplete</code> plugin, which you can utilize after adding or removing a class that applies a CSS transition.</p>

    </div><!--/content-secondary -->		
	
	<div class="content-secondary">
		
		<div data-role="collapsible" data-collapsed="true" data-theme="b">
			
				<h3>More in this section</h3>
				
				<ul data-role="listview" data-theme="c" data-dividertheme="d">
				
					<li data-role="list-divider">API</li>
					<li><a href="../../docs/api/globalconfig.html">Configuring defaults</a></li>
					<li data-theme="a"><a href="../../docs/api/events.html">Events</a></li>
					<li><a href="../../docs/api/methods.html">Methods &amp; Utilities</a></li>
					<li><a href="../../docs/api/mediahelpers.html">Responsive Layout</a></li> 
					<li><a href="../../docs/api/themes.html">Theme framework</a></li>
	
				</ul>
		</div>
	</div>		

</div><!-- /content -->

<div data-role="footer" class="footer-docs" data-theme="c">
		<p>&copy; 2011 The jQuery Project</p>
</div>
	
</div><!-- /page -->

</body>
</html>